Update dependencies graph (pr #94 fixups) #98
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…scription In this commit, I've updated the dependency graph to the Bitcoin 29.0 (The actual maintained version for bitcoin Core). This graph show the entire dependencies links between various library of the code base structure.
Added the missing id tag to link the documentation to the HTML file generated by jekyll on build
Contributor
|
Hello @willcl-ark , I just checked it. Thanks you for counting my commits and thanks for having time to review the work. Its good. Appreciate. |
Collaborator
Author
|
Great, so you’re happy for me to merge this one (with your commits in) then? |
Contributor
|
Yes ! 😁😁. Thanks 😁 I’ll continue to learn and improve for next times😃 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hey @heyolaniran, I've made a few changes to your PR in this branch, rather than force-pusing to your PR:
If you are happy for me to use your commits in this PR (and perhaps review it? 🙏🏼), then I'd be happy to merge this one.
Sorry for the slow review/turnaround.